Summary

Linked issue(s)

Closes #

Type of change

• feat — user-visible new feature
• fix — user-visible bug fix
• perf — performance improvement
• refactor — code change, no behaviour change
• docs — documentation only
• test — tests only
• build — build system, packaging, dependencies
• ci — CI configuration
• chore — maintenance
• revert — revert of a prior commit

Breaking change?

• This PR introduces a breaking change.

How has this been tested?

Checklist

• My PR title follows Conventional Commits.
• All of my commits are signed and show "Verified" on GitHub
  (GPG or SSH). See
  CONTRIBUTING.md § Signed commits.
• All of my commits have a DCO sign-off (Signed-off-by: trailer,
  added by git commit -s).
• My branch name follows <type>/<short-kebab-description> (see
  CONTRIBUTING.md § Branch naming).
• I have rebased onto the latest default branch; no merge commits
  from the base branch in this PR.
• I have added or updated tests covering the change (or explained
  below why tests aren't applicable).
• I have updated documentation (README, inline docs, changelog,
  migration notes) where relevant.
• I ran the repo's local checks (lint, typecheck, tests) and they pass.
• Any new runtime dependencies are justified in this PR description
  (name, version, license, why).
• If this is a breaking change, I have marked the box above and
  included a BREAKING CHANGE: footer in at least one commit.

Screenshots / recordings

Additional notes